Internet Surfer 2.0/Internet Surfer 2.0 (Wayzata Technology) (1996).iso/pc/text/mac/faqs.438

Text File | 1996-02-12 | 27.8 KB | 667 lines

Frequently Asked Questions (FAQS);faqs.438



xwindows/xshowgif:
README.1st          ;Installation notes for xshowgif
xshowgif.tar.Z      ;Compressed tar file for xshowgif

xwindows/xv:
README.1st          ;Installation notes for xv v. 2.00
xv2.tar.Z           ;Compressed tarfile for xv v. 2.00

xwindows/xviewgl:
README.1st          ;Installation notes for xviewgl
xviewgl_v1.0.tar.Z  ;Compressed tar file for xviewgl
-------------------------------------------------------------------------------

That's about it for this introduction.  If you have any suggestions
for things to include in future versions, don't hesitate to let me
know...

         ~ deej ~              | (If I were expressing Cadence's opinions, )
Jim Howard -- [e-mail] | (they'd probably make me wear a tie...    )
        (^:=             Flames cheerfully ignored.             =:^)
"I tell you this:  no eternal reward will forgive us now
 for wasting the dawn" -- Jim Morrison, The Doors
Xref: bloom-picayune.mit.edu news.misc:8888 news.answers:3056
Path: bloom-picayune.mit.edu!snorkelwacker.mit.edu!spool.mu.edu!news.cs.indiana.edu!purdue!spaf
From: [e-mail] (Gene Spafford)
Newsgroups: news.misc,news.answers
Subject: Changes to Rules for posting to Usenet
Message-ID: <[e-mail]>
Date: 20 Sep 92 04:17:52 GMT
Expires: 19 Nov 92 16:17:52 GMT
Followup-To: news.misc
Organization: Dept. of Computer Sciences, Purdue Univ.
Lines: 29
Approved: [e-mail]
Supersedes: <[e-mail]>

Archive-name: posting-rules/diff1
Last-change: 3 Sep 1992 by [e-mail] (Dan Jacobson)


*** old/rules.n    Mon Jul 20 01:49:28 1992
--- ./src/rules.n    Thu Sep  3 21:31:31 1992
***************
*** 5,7 ****
  Original-author: [e-mail] (Mark Horton)
! Last-change: 11 May 1992 by [e-mail] (Barry Margolin)

--- 5,7 ----
  Original-author: [e-mail] (Mark Horton)
! Last-change: 3 Sep 1992 by [e-mail] (Dan Jacobson)

***************
*** 199,201 ****
  question that's answered there, you'll likely receive a number of
! responses that scream "RTFM" (Read the F* Manual).

--- 199,201 ----
  question that's answered there, you'll likely receive a number of
! responses that scream "RTFM" (Read the F*ing Manual).

--
Gene Spafford
Software Engineering Research Center & Dept. of Computer Sciences
Purdue University, W. Lafayette IN 47907-1398
Internet:  [e-mail]    phone:  [phone]
Xref: bloom-picayune.mit.edu news.announce.newusers:914 news.answers:3558
Path: bloom-picayune.mit.edu!snorkelwacker.mit.edu!mojo.eng.umd.edu!darwin.sura.net!wupost!cs.utexas.edu!sun-barr!ames!purdue!spaf
From: [e-mail] (Gene Spafford)
Newsgroups: news.announce.newusers,news.answers
Subject: Rules for posting to Usenet
Message-ID: <[e-mail]>
Date: 19 Oct 92 05:14:19 GMT
Expires: 18 Dec 92 17:14:18 GMT
Followup-To: news.newusers.questions
Organization: Dept. of Computer Sciences, Purdue Univ.
Lines: 255
Approved: [e-mail]
Supersedes: <[e-mail]>

Archive-name: posting-rules/part1
Original-author: [e-mail] (Mark Horton)
Last-change: 3 Sep 1992 by [e-mail] (Dan Jacobson)

This message describes some of the rules of conduct on Usenet.  The rules
vary depending on the newsgroup.


Some newsgroups are intended for discussions and some for announcements
or queries.  It is not usually a good idea to carry on discussions in
newsgroups that are designated otherwise.  It is never a good idea to
carry on "meta-discussions" about whether a given discussion is
appropriate -- such traffic mushrooms until nobody can find articles
that belong.  If you are unhappy with what some user said, send him/her
mail, don't post it.


Before posting, think about where your article is going.  If it's
posted to a "comp", "news", "misc", "soc", "sci", "rec" or "talk"
newsgroup, it will probably go to the USA, Canada, Europe, Australia,
and many countries in Asia.  Certain articles are only of local
interest (e.g. used car ads) and it is inappropriate to post them to
the whole world.  Use the "Distribution" feature to restrict
distribution to your local area.  If you don't know how to use this
feature, read "Frequently Submitted Items" in another article in
news.announce.newusers. (Note, however, that some sites have broken
software or improperly configured news systems, so sometimes use of a
"Distribution" header may not work.)


Be considerate with your use of network resources.  Your individual
usage may not seem like much compared to the net as a whole, but in
aggregate, small savings in disk or CPU add up to a great deal.  For
instance, messages offering thanks, jibes, or congratulations will
only need to be seen by the interested parties -- send these by mail
rather than posting them. The same goes for simple questions, and
especially for any form of "me too" posting.

To help minimize some transfer load and disk usage throughout the
Usenet, consider not only how many groups should carry your posting
over what distribution area, but also how long it will be useful. Many
kinds of postings -- such as those making announcements or offers --
have a obvious useful lifetime. Posted questions that aren't answered
within a decent interval probably won't be answered at all, and
announcements will have a limited lifetime. All such postings will be
using bandwidth to no purpose after a certain time.  When making such
postings one should determine what that time interval is, based upon
the nature of the posting, the volume of articles on the newsgroup(s)
involved, and the habits of the audience, if known. Then include an
expiration date in the posting. This will mark the date after which
the article should not be retained at each site.

To include an expiration date in an article, when posting insert a
line in the header below the "Newsgroups:" line with the expiration.
For instance, type "Expires: 5 Feb 92" to have the article expire
after Feb 5, 1992.  Most news software will also accept expiration
dates of the form "Expires: +5days".  Please do NOT set expiration
dates far into the future simply to have the article stay around.
Many sites expire old articles no matter what the header indicates, so
you are unlikely to achieve much other than clutter the disk on a few
sites.  Default expiration is normally in the range of 7 to 21 days,
depending on disk space at each site.


Don't post announcements regarding major news events (e.g. the space
shuttle has just exploded!) to news groups.  By the time most people
receive such items, they will long since have been informed by
conventional media.  If you wish to discuss such an event on the net,
use the "misc.headlines" newsgroup.


Announcement of professional products or services on Usenet is allowed;
however, since someone else is paying the phone bills for this, it is
important that it be of overall benefit to Usenet.  Post to the
appropriate newsgroup -- comp.newprod -- never to a general purpose
newsgroup such as "misc.misc".  Clearly mark your article as a product
announcement in the subject.  Never repeat these -- one article per
product at the most; preferably group everything into one article.
Advertising hype is especially frowned upon -- stick to technical
facts.  Obnoxious or inappropriate announcements or articles violating
this policy will generally be rejected.  This policy is, of course,
subject to change if it becomes a problem.


Some newsgroups are moderated.  In these groups, you cannot post
directly, either by convention or because the software prevents it.  To
post to these newsgroups, send mail to the moderator. Examples:

Newsgroup        Moderator    Purpose
---------        ---------    -------
news.announce.important stargate!announce    Important announcements for everyone
comp.std.unix        uunet!std-unix    Unix standards discussion
comp.std.mumps        plus5!std-mumps    ANSI Mumps standards discussion
comp.unix        zorba!modunix    Discussion of Unix* features and bugs

Some newsgroups have special purpose rules:

Newsgroup        Rules
---------        -----
news.announce.important    Moderated, no direct postings, important things only.
misc.wanted        Queries, "I want an x", "Anyone want my x?".  No
            discussions. Don't post to more than one xxx.wanted.
            Use the smallest appropriate wanted (e.g. used car
            ads to nj.wanted.)
            Requests for sources, termcaps, etc. should go to the
            "comp.sources.wanted" newsgroup.
rec.humor        Clean humor only; anything offensive must be rotated;
            no discussions -- humor only.  Discussions go in
            rec.humor.d
rec.arts.movies        Don't post anything revealing part of a movie
            without marking it (spoiler) in the subject.
rec.arts.*        Same as movies -- mark spoilers in the subject line.
news.groups        Discussions about new groups: whether to create
            them and what to call them.  Don't post yes/no
            votes, mail them to the author
misc.test        Use the smallest test group possible, e.g.
            "test" or "ucb.test".  Say in the body of the
            message what you are testing.


It is perfectly legal to reproduce short extracts of a copyrighted work
for critical purposes, but reproduction in whole is strictly and
explicitly forbidden by US and international copyright law.  (Otherwise,
there would be no way for the artist to make money, and there would
thus be less motive for people to go to the trouble of making their art
available at all.  The crime of theft is as serious in this context as
any other, even though you may not have to pick locks, mask your face,
or conceal merchandise.)

It is generally considered rude to post private e-mail correspondence
without the permission of the author of that mail.  Furthermore, under
copyright statutes, the author of the e-mail possesses a copyright on
mail that he or she wrote; posting it to the net or mailing it on to
others without permission of the author is likely a violation of that
copyright as well as being rude.

All opinions or statements made in messages posted to Usenet should be
taken as the opinions of the person who wrote the message.  They do not
necessarily represent the opinions of the employer of that person, the
owner of the computer from which the message was posted, or anyone
involved with Usenet or the underlying networks of which Usenet is made
up.  All responsibility for statements made in Usenet messages rests
with the individual posting the message.


Posting of information on Usenet is to be viewed as similar to
publication.  Because of this, do not post instructions for how to do
some illegal act (such as jamming radar or obtaining cable TV service
illegally); also do not ask how to do illegal acts by posting to the
net.


If you have a standard signature you like to append to your articles,
put it in a file called .signature in your home directory.  "postnews"
and "inews" will automatically append it to your article.  Please keep
your signatures concise, as people do not appreciate seeing lengthy
signatures, nor paying the phone bills to repeatedly transmit them.  2
or 3 lines are usually plenty.  Sometimes it is also appropriate to add
another line or two for addresses on other major networks where you can
be reached (e.g., Internet, Bitnet).  Long signatures are
definitely frowned upon.  DO NOT include drawings, pictures, maps, or
other graphics in your signature -- it is not the appropriate place
for such material and is viewed as rude by other readers.


If you post an article and remember something you've left out or
realize you've made a factual error, you can cancel the article and (if
canceled quickly enough) prevent its distribution.  Then you can
correct whatever was wrong and post a new copy.  In "rn" and
"readnews", an article that you posted can be canceled with the "C"
command.  Be aware, however, that some people may have already read the
incorrect version so the sooner you cancel something, the better.


Before posting a question to the net (especially one that you think
will be easy for experts to answer), consider carefully whether
posting is the most appropriate way to get the answer.  There are many
ways to find answers without using up network resources and forcing
thousands of people to read your question (and several helpful
volunteers to spend time responding).  Many newsgroups have a
Frequently Asked Questions (FAQ) list that is posted periodically
(usually about once a month), and they are also usually cross-posted
to news.answers.  They usually have explicit expiration dates set, so
they shouldn't be expired until a new version has been posted, so if
you can't find the FAQ in either the newsgroup or news.answers, there
probably isn't one (thus, it's probably not useful to post a question
asking whether there is one).  If you have local experts (or simply
more experienced users than yourself) at your site, try asking them
before posting.  If you're trying to find where you can FTP software
or a newsgroup archive, try using the Archie service; see postings in
news.answers for details.  Many newsgroups are also archived in Wide
Area Information Service (WAIS) databases; WAIS client software may be
FTPed from ftp.think.com, or you may use WAIS by telnetting to
quake.think.com and logging in as "wais".  Finally, you should also
check the manuals for your system; if you don't, and you post a
question that's answered there, you'll likely receive a number of
responses that scream "RTFM" (Read the F*ing Manual).


If the news system rejects a followup due to "more quoted lines than
new text," please do not use "filler" lines to make up for this.
Instead, if after careful editing, you have more to quote than to
write, change the citation character.  For example, in the display
editor vi, you could use the incantation:
    :%s/^>/</
Be careful not to do the very similar:
    :%s/>/</
which will affect >'s that are not being used as the citation
character.  (In particular, it will damage the "References" line in the
article header.)


In preparing an article, be aware that other people's machines are
not the same as yours.  The following is a list of things to keep
in mind:
 * Except for source, keep your lines under 80 characters, and
   under 72 if possible.  (most editors have a fill or format
   mode that will do this for you automatically)
 * Right justified text may look "prettier" in some sense, but it
   is almost always harder to read than leaving ragged right
   margins; don't justify your articles.
 * Most special control characters will not work for most readers.
   In fact, the  space character is about the only one
   you can be sure will work consistently. Even tabs aren't always
   the same from machine to machine, and should be avoided.  Many mail
   agents will strip or remap control characters.
 * Pictures and diagrams should not use embedded tabs.
 * Refer to articles by Message-ID, and never by article number.
 * What you think is the previous article is unlikely to be so elsewhere.
 * Submissions in a single case (all upper or all lower) are
   difficult to read.


In general, when a mailing to somebody fails, DON'T post a message
about it!  Think for a moment: you are trying to send something to
someone on ONE system.  Your message might go through (at most) TEN
systems on the way there.  Posting a message in the news sends it to
many thousands of systems throughout the world!  There is no way to
justify adding to the news load of all those machines simply because
you cannot determine how to get your mail through.

If your message is important, contact someone who knows more about the
mail system and who might be able to help you get your message
through.  Your local system administrator, for instance, or the admin
of the next site "upstream," might be able to help. You can also send
mail to "postmaster" at one of the major Usenet sites.  Almost all of
these people would rather see an occasional plea for help in their
mailbox than read another broadcast in the news system.  If your
message is *really* important, pick up the phone and try to call the
other person.
--
Gene Spafford
Software Engineering Research Center & Dept. of Computer Sciences
Purdue University, W. Lafayette IN 47907-1398
Internet:  [e-mail]    phone:  [phone]
Xref: bloom-picayune.mit.edu comp.protocols.ppp:1106 news.answers:4742
Path: bloom-picayune.mit.edu!enterpoop.mit.edu!eru.mt.luth.se!lunic!sunic!mcsun!Germany.EU.net!olymp!ignatios
From: [e-mail] (Ignatios Souvatzis)
Newsgroups: comp.protocols.ppp,news.answers
Subject: point-to-point protocol: frequently wanted answers
Summary: This newsgroup contains information about the Internet Point-to-Point
    Protocol, including a bibliography, a list of public domain and
    commercial software and hardware implementations, a section on
    configuration hints and a list of frequently asked ques
Message-ID: <ppp-faq/[e-mail]>
Date: 21 Dec 92 19:13:01 GMT
Expires: Mon, 11 Jan 1993 19:11:02 GMT
Sender: [e-mail]
Followup-To: poster
Organization: computer science department, university of Bonn, Germany
Lines: 939
Approved: [e-mail]

Archive-name: ppp-faq/part1
Version: 2.3
Last-modified: Tue Dec 15 12:34:18 MET 1992

0.1 Introduction

I took the Information in Ed Vielmetti's FAQ files, my personal experience,
and lots of stuff from comp.protocols.ppp, and built a new one for them.
This posting will be reposted fortnightly, as soon as it is fairly stable,
and weekly till then. Changed sections are marked in the index with a ! or
+ for something got added or - for something got deleted.

The major sections start with a ^L, so hit the spacebar on the --more--
prompt.

0.2 Information wanted:

If you have experience with anything mentioned here, or know of newer
versions, or of versions of software for other hardware/OS, or ...

send me mail. I'll include it and possibly mention your name, if you don't
express otherwise.

1. INDEX TO THE FAQ:

2. What is PPP?

2.1 Introduction
2.2 PPP features which may or may not be present
2.3 PPP glossary
2.4 PPP-relevant RFC's

3.1 How to:
3.1 connect a single host to a network without needing a new subnet.
3.2 configure KA9Q PPP and it's Unix counterpart
+3.3 configure NCSA with the merit ppp driver and its unix counterpart
!3.4 work BOOTP over protocols such as SLIP or PPP

4. Real PPP questions with answers
4.1 Does somebody have a patent on PPP? [no]
4.2 Is it possible to use PPP as link layer in ISDN? [yes]

5. Free PPP software packages.

5.1 free PPP FOR SunOS 4.1.x:
5.1.1.1 ppp-1.1.tar.Z, works also on BSD (386BSD: 0.0 only)
5.1.1.2 pppd-1.01.tar.Z
5.1.2 dp-2.2.tar.Z
5.1.3 Perkins/Clements/Fox/Christy PPP for SunOS

5.2 free PPP for BSD:
5.2.1 ppp-1.1.tar.Z, see 4.1.1.1

5.3 free PPP for SYSVR4:

5.4 FREE PPP FOR MSDOS:

5.4.1 KA9Q NOS ppp additions:
5.4.2 PPP for NCSA telnet:

5.5 free PPP for AmigaOS:
5.5.1 AmigaNOS (KA9Q NOS for Amiga):

5.6 free PPP for NeXT:

5.7 free PPP for Macintosh:

6. ftp sites for PPP stuff, docs etc.

7. Commercial PPP software packages.
7.1 Amiga Inet:
7.2 Commercial PPP packages for MS-DOS and MS-Windows
+7.2.1 MSDOS with and without MSWindows

+7.2.1.1.  LAN WorkPlace for DOS 4.1 beta (see also 7.2.2)
+7.2.1.2.  PC/TCP 2.11
+7.2.1.3.  Distinct TCP/IP 3.0 beta
+7.2.1.4.  Super-PPP for Windows 1.0 beta
!7.2.2 MSDOS/Novell:

-7.3 for other computers:

8. PPP hardware.
8.1 Hardware that does async PPP
8.2 Hardware that supports sync PPP
8.3 Recent summaries stuff from the net, will be merged with the rest later

+9. (incomplete) Acknowledgements

2. What is PPP?

2.1 Introduction
PPP is the Internet Standard for transmission of IP packets over serial
lines. PPP supports async and sync lines. For a general discussion of PPP,
and of the PPP vs. SLIP question, look at the paper

ftp.uu.net:vendor/MorningStar/papers/sug91-cheapIP.ps.Z

2.2 PPP features which may or may not be present

Above and beyond compatibility with basic PPP framing, note whether
the software implements the following features.  Not all features are
needed or even desired in every product.

- "demand-dial".  Bring up a PPP interface and dial the phone when
  packets are queued for delivery; bring the interface down after some
  period of inactivity.

- "redial".  (For lack of a better term).  Bring up a PPP
  interface whenever it goes down, to keep a line up.

- "scripting".  Negotiate through a series of prompts or intermediate
  connections to bring up a PPP link, much like the sequence of events
  used to bring up a UUCP link.

- "parallel".  Configure several PPP lines to the same destination and
  do load sharing between them.  (Not standardized, usually only see
  in SLIP implementations, noted there as "parallel-slip".)

- "filtering".  Select which packets to send down a link or whether to
  bring up a "demand-dial" link based on IP or TCP packet type or TOS,
  e.g. don't dial the phone for ICMP ping packets.

- "header compression".  TCP header compression according to RFC 1144.
  Marginally useful on high speed lines, essential for low speed lines.

- "server".  Accept incoming PPP connections, which might well also
  include doing the right things with routing.

- "tunneling". build a virtual network over a PPP link across a TCP stream
   through an existing IP network

- "extra escaping". byte-stuffing characters outside the negotiated
  asyncmap, configurable in advance but not negotiable

2.3 PPP glossary

From: [e-mail] (Edward Vielmetti) [and others]
Subject: PPP glossary

Every new technology breeds its own set of acronyms.  PPP is no
different.  Here is a glossary of sorts.

ack    Acknowledgement.
AO    Active open [state diagram] (no lonter part of the FSM as of RFC 1331)
C    Close [state diagram]
CHAP    Challenge-Handshake Authentication Protocol (RFC 1334)
D    Lower layer down [state diagram]
DES    Data Encryption Standard
DNA    Digital Network Architecture
IETF    Internet Engineering Task Force.
IP    Internet Protocol
IPCP    IP Control Protocol.
IPX    Internetwork Packet Exchange (Novell's networking stack)
FCS    Frame Check Sequence [X.25]
LCP    Link Control Protcol.
LQR    Link Quality Report.
MD4    MD4 digital signature algorithm
MD5    MD5 digital signature algorithm
MRU    Maximum Receive Unit
MTU    Maximum Transmission Unit
nak    Negative Acknowledgement
NCP    Network Control Protocol.
NRZ    Non-Return to Zero bit encoding. (SYNC ppp default because of
    availability)
NRZI    Non-Return to Zero Inverted bit encoding. (SYNC ppp preferred
    alternative to NRZ)
OSI    Open Systems Interconnect
PAP    Password Authentication Protocol (RFC 1334)
PDU    Protocol Data Unit (i.e., packet)
PO    Passive open [no longer part of state diagram]
PPP    Point to Point Protocol (RFC 1331, 1332, 1333, 1334, 1376, 1377, 1378)
RCA    Receive Configure-Ack [state diagram]
RCJ    Receive Code-Reject [state diagram]
RCN    Receive Configure-Nak or -Reject [state diagram]
RCR+    Receive good Configure-Request [state diagram]
RER    Receive Echo-Request [no longer part of state diagram]
RFC    Request for Comments (internet standard)
RTA    Receive Terminate-Ack [state diagram]
RTR    Receive Terminate-Request [state diagram]
RUC    Receive unknown code [state diagram]
sca    Send Configure-Ack [state diagram]
scj    Send Code-Reject [state diagram]
scn    Send Configure-Nak or -Reject [state diagram]
scr    Send Configure-Request [state diagram]
ser    Send Echo-Reply [no longer part of state diagram]
sta    Send Terminate-Ack [state diagram]
str    Send Terminate-Request [state diagram]
ST-II    Stream Protocol
TO+    Timeout with counter > 0 [state diagram]
TO-    Timeout with counter expired [state diagram]
VJ    Van Jacobson (RFC 1144 header compression algorithm)
XNS    Xerox Network Services

2.4 PPP relevant RFC's:

Here's a list with descriptions.  Note some of these are obsolete.

1378  PPP AppleTalk Control Protocol (ATCP). Parker, B.  1992 November; 16 p.
      (Format: TXT=28496 bytes)

1377  PPP OSI Network Layer Control Protocol (OSINLCP). Katz, D.  1992
      November; 10 p. (Format: TXT=22109 bytes)

1376  PPP DECnet Phase IV Control Protocol (DNCP). Senum, S.J.  1992 November;
      6 p. (Format: TXT=12448 bytes)

1334  PPP authentication protocols. Lloyd, B.; Simpson, W.A.  1992 October;
      16 p. (Format: TXT=33248 bytes)

1333  PPP link quality monitoring. Simpson, W.A.  1992 May; 15 p. (Format:
      TXT=29965 bytes)

1332  PPP Internet Protocol Control Protocol (IPCP). McGregor, G.  1992 May;
      12 p. (Format: TXT=17613 bytes)  (Obsoletes RFC 1172)

1331  Point-to-Point Protocol (PPP) for the transmission of multi-protocol
      datagrams over point-to-point links. Simpson, W.A.  1992 May; 66 p.
      (Format: TXT=129892 bytes)  (Obsoletes RFC 1171, RFC 1172)

1220  Point-to-Point Protocol extensions for bridging. Baker, F.,ed.  1991
      April; 18 p. (Format: TXT=38165 bytes)

1172  Point-to-Point Protocol (PPP) initial configuration options. Perkins,
      D.; Hobby, R.  1990 July; 38 p. (Format: TXT=76132 bytes)  (Obsoleted by
      RFC 1331, RFC 1332)

1171  Point-to-Point Protocol for the transmission of multi-protocol datagrams
      over Point-to-Point links. Perkins, D.  1990 July; 48 p. (Format:
      TXT=92321 bytes)  (Obsoletes RFC 1134; Obsoleted by RFC 1331)

1134  Point-to-Point Protocol: A proposal for multi-protocol transmission of
      datagrams over Point-to-Point links. Perkins, D.  1989 November; 38 p.
      (Format: TXT=87352 bytes)  (Obsoleted by RFC 1171)


[e-mail] (Bob Sutterfield) wrote in comp.protocols.ppp
(Message-ID: <[e-mail]>):

All of 1134, 1171, and 1172 (and 1055, for that matter :-) have been
obsoleted.  They're interesting only if you want to debug a connection
with an ancient PPP implementation, and you're wondering why (e.g.) it
asked you for IPCP option 2 with a length of only 4, and
Compression-Type 0x0037.

(There's a lot of that still running around - be careful out there.)


3. HOW TO ... :

3.0 complain about missing or incorrect information in the FAQ list

E-mail to [e-mail] (Ignatios Souvatzis), and add
information I'll need to think about it. That is:

- In case of incorrect information, send me the correct information and the
   source of it.

- In case of missing information, send me the information which is missing and
  the source of it.

3.1 connect a single host to a network without needing a new subnet.

From: [e-mail] (Ignatios Souvatzis)

If you have only one single machine on the other side, the easiest way
is to give it a IP address belonging to the local ethernet/IP subnet,
and to tell the ppp gateway machine to advertise (proxy arp) its own
ethernet address as the other machines'. Works like a charm here. Of
course, for a large group or complicated network on the other side,
you would get more management problems.

On the gateway do:

arp -s othermachinesipaddress myownethernetaddress permanent public
ifconfig pppNUMBER myipaddress othermachinesipaddress [other params] up

on remote machine:

ifconfig pppNUMBER gatewaysipaddress [other params] up
route add default gatewaysipaddress 1

pppNUMBER might be spelled as dpNUMBER for dialup IP.

Of course, if you use routeing daemons, you could also propagate the
route via routed / gated etc. to other machines, but it's more painful
because every machine has to do it (and might choose not to do it),
and every machine doing IP on a Ethernet HAS to talk arp.

On intermittently connected demand-dialed links, you may need to edit
/etc/gateways to define the destination of the PPP or SLIP connection
as a "passive" link.  Otherwise, routed will remove routes from the
kernel's routing table that use that link, because it won't hear RIPs
coming from hosts or routers across the wire.  Since it doesn't hear
anything from hosts or routers on the far side of the wire, routed
assumes that the link is dead forever.


3.2 configure KA9Q PPP and it's Unix counterpart

Newsgroups: comp.protocols.ppp
From: [e-mail] (Kim Toms)
Subject: Re: PPP for DOS? (good info for FAQ)
Date: Wed, 9 Dec 1992 06:26:28 GMT

I have been able to use the ka9q software on my PC to call my Suns at
work.  This is available from merit.edu:/pub/ppp/ka9q.zip. I had to
tell our Sun product [that would be Morningstar PPP, see below. I.S.]
"nolqm" in order to prevent it from hanging up because of an lqm
failure, but other than that, I have had no trouble.